Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1357

reference: 312-tree-1
name: 1357
tree-preservation-order: undefined
312-tpo-1
uprn
address-text
point: POINT (-1.026544 50.893213)
geometry: MULTIPOLYGON (((-1.026473 50.893206,-1.026476 50.893219,-1.026486 50.893232,-1.026502 50.893242,-1.026521 50.893249,-1.026543 50.893251,-1.026565 50.893249,-1.026585 50.893243,-1.026601 50.893233,-1.026612 50.893221,-1.026615 50.893207,-1.026612 50.893193,-1.026602 50.893180,-1.026587 50.893170,-1.026567 50.893164,-1.026545 50.893161,-1.026523 50.893163,-1.026503 50.893169,-1.026487 50.893179,-1.026477 50.893192,-1.026473 50.893206)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL